%%This is a very basic article template.
%%There is just one section and two subsections.
\documentclass{article}

\begin{document}


\section{Miscellaneous}

\subsection{Terminology}

\begin{description}
\item[Subject]
\item[Composition] Retrieving information from subjects in order to form a
runing program.
\item[Composition rule] A rule that guides/decides how composition is done
\item[Requirement-based development]  The code that implements a new
	requirement is built as a coherent subject rather than being interleaved
	amongst other application code in a manner that makes it difficult to
	identify and maintain \cite{decent}
\item[Binary Composition] Subjects are compiled independently, with method
	calls and whatnot being routed at the linking phase, with the assistance of a
	``Subject schema''
\item[Subject schema] Defines the classes provided and/or used by the subject,
	and their classification hierarchy and instance variables from the point of
	view of this subject.\cite{decent}
\end{description}

\subsection{Pros and cons}

\subsubsection{Pros}
\begin{itemize}
  \item No need for a class owner. \cite{decent}
  \item A subject can easily be reused in some other project \cite{decent}
  \item A subject can easily be executed on another machine \cite{decent}
  \textit{Requires binary separation of subjects}
\end{itemize}


\subsection{Interesting quotes}
\begin{quotation}
Neither source code access nor recompilation
are required to perform this composition, allowing extension and composition of object-code-only appli-
cations.\cite{decent}
\end{quotation}

\begin{quotation}
Customers would benefit directly from subject-oriented programming, in addition to benefitting indirectly
from improved application development and maintenance. A software product bought as a composition
of subjects could be reconfigured according to local requirements or preferences, could be extended by
composition with other subjects (from the same supplier, different suppliers or written in-house), and could
serve as a library of reusable parts. All configuration and composition could be done without access to
source code.\cite{decent}
\end{quotation}

\begin{quotation}
A subject-oriented application, or suite of applications, is constructed by  composing a collection of sub-
jects. Each subject is itself an object-oriented program, though often an incomplete one. It consists of a
collection of classes (arranged in a classification hierarchy, as is standard, though this is incidental). It is
written in a standard object-oriented language.\cite{decent}
\end{quotation}

\begin{quotation}
The combined class definition is one piece of code, which in any reasonable
approach must be programmed and maintained by one person\ldots \cite{decent}
\textit{They wouldn't have liked Extreme Programming :)}
\end{quotation}


\bibliographystyle{plain}
\bibliography{bibliography}
\end{document}
